Home
Integrating
HCL Launch supports integrations with other IBM® products, products from others, and certain cloud systems.
Deploying components to the z/OS® platform
Use the toolkit to deploy to the IBM® z/OS® platform.
Creating z/OS® component versions
You can create z/OS component version by running the buztool.sh command from job control language (JCL) or from the z/OS® UNIX™ System Services command line. You can also create z/OS component version by using the z/OS File Source Config plug-in.

Integrating
HCL Launch supports integrations with other IBM® products, products from others, and certain cloud systems.
- Integrating with HCL OneTest
  When you use OneTest™ Performance, you can create tests and run those tests in HCL Launch by using the HCL OneTest™ Performance Launch plugin.
- z/OS considerations for HCL Launch
  HCL Launch includes support for the z/OS platform. Although the articles in this Knowledge Center for using HCL Launch to deploy applications, certain platform-specific configuration factors must be considered when using a z/OS model.
- Deploying components to the z/OS® platform
  Use the toolkit to deploy to the IBM® z/OS® platform.
  - Ship list files
    The ship list file describes the files from the build to include in the new component version to deploy. Ship list files can also use generic artifacts to describe changes that are not physical files, such as configuration changes.
  - Generating Ship list for Endevor and Changeman packages
    You can generate shiplist.xml using Endevor SCL and Changeman configurations. Generated shiplist.xml can later be used to create component version using buztool.sh.
  - Searching the z/OS environment inventory
    The z/OS search feature is available for any application that contains a z/OS type component. Search is performed for a specific file in the artifacts belonging to the z/OS components deployed to that environment.
  - Creating z/OS® component versions
    You can create z/OS component version by running the buztool.sh command from job control language (JCL) or from the z/OS® UNIX™ System Services command line. You can also create z/OS component version by using the z/OS File Source Config plug-in.
    - Creating z/OS® component versions from JCL
      To create IBM® z/OS® component versions from job control language (JCL), create and submit JCL to run the buztool.sh command.
    - Creating z/OS® component versions from z/OS® UNIX™ System Services
      To create IBM® z/OS® component versions from z/OS UNIX™ System Services, submit the buztool.sh command from a z/OS UNIX shell.
    - Creating z/OS® component version using the v2 package format
      Starting with HCL Launch version 7.0.5, you can create IBM® z/OS® component versions from a new package version called version 2 or v2. You can create v2 component versions using the buztool.sh command.
    - Merging z/OS component versions
      Two or more z/OS component versions can be merged from a snapshot into one component version to simplify the deployment to the next environment. Merging component versions in this way avoids deploying intermediate programs into production.
  - Security requirements on IBM® z/OS® computers
    Specific security definitions are used to secure HCL Launch functions for the IBM® z/OS® environment. To deploy applications to an IBM z/OS environment, the user accounts on the agent computer must have adequate access permissions. You must also identify specific directories and data sets to the authorized program facility.
  - Troubleshooting problems on z/OS®
    To troubleshoot problems on agent computers that are running IBM® z/OS®, examine the agent log files.

Creating z/OS® component versions

You can create z/OS component version by running the buztool.sh command from job control language (JCL) or from the z/OS® UNIX™ System Services command line. You can also create z/OS component version by using the z/OS® File Source Config plug-in.

About this task

In an automated system, typically, you write a script that runs the buztool.sh command after a build is created by your build system. The buztool.sh command then creates a component version which can be deployed using a deploy process.

HCL Launch server requires the time zone of the z/OS system to display the artifact modified date accurately. Identify the time zone of the z/OS system and set the TZ environment variable. To know more about the TZ environment variable, refer to the z/OS® documentation.

While packaging load modules, System Status Index (SSI) value is converted to epoch time and displayed as Last Modified Date in the component version page. For example, if a load module SSI value is 087ab85c. Converting to decimal format gives the Epoch time as 142260316 which is displayed as July 5, 1974 12:45:16 PM GMT in the component version page. For non-load modules, the buztool.sh command tries to read ZLM4DATE, ZLMTIME and ZLMSEC statistical values from ISPF.

When you create a z/OS component version with an external repository, you will store artifacts in the external repository and store only the metadata of artifacts in Codestation. Hence, when you download the version by using the Download All action on the web application, only the metadata XML file, which is stored in Codestation, is displayed in the packageManifest.xml file.

What to do next

You can work with the component that contains z/OS® files as you would work with any other component in HCL Launch. Use the z/OS® Utility plug-in to create processes that deploy components that contain z/OS® files.

See the HCL Launch website for information about the z/OS® Utility plug-in: Plugins.

Note: IMS.TFORMAT members (member name containing non-readable characters) are not supported. PDS members name can have ONLY [0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ@#$] characters.